Power management for remote antenna units in distributed antenna systems

ABSTRACT

Power management for a remote antenna unit(s) (RAUs) in a distributed antenna system. Power can be managed for an RAU configured to power modules and devices that may require more power to operate than power available to the RAU. For example, the RAU may be configured to include power-consuming RAU modules to provide distributed antenna system-related services. As another example, the RAU may be configured to provide power through powered ports in the RAU to external power-consuming devices. Depending on the configuration of the RAU, the power-consuming RAU modules and/or external power-consuming devices may demand more power than is available at the RAU. In this instance, the power available at the RAU can be distributed to the power-consuming modules and devices based on the priority of services desired to be provided by the RAU.

PRIORITY CLAIM

This application is a continuation of U.S. application Ser. No.14/845,768, filed Sep. 4, 2015, which is a continuation of U.S.application Ser. No. 13/860,017, filed Apr. 10, 2013, which is acontinuation of International Application No. PCT/US11/55861 filed Oct.12, 2011, which claims the benefit of priority to U.S. ProvisionalApplication No. 61/392,687, filed on Oct. 13, 2010, all of which areincorporated herein by reference.

RELATED APPLICATIONS

The present application is related to U.S. application Ser. No.13/859,985, filed Apr. 10, 2013 and entitled “Local Power Management forRemote Antenna Units in Distributed Antenna Systems,” now U.S. Pat. No.9,160,449, which claims priority to U.S. Provisional Application No.61/392,660, filed on Oct. 13, 2010, both of which are incorporatedherein by reference in their entireties. This application is alsorelated to U.S. application Ser. No. 14/845,946, filed Sep. 4, 2015.

The present application is also related to U.S. Provisional ApplicationNo. 61/330,386 filed on May 2, 2010 and entitled “Providing Digital DataServices in Optical Fiber-Based Distributed Radio Frequency (RF)Communications Systems, and Related Components and Methods,” which isincorporated herein by reference in its entirety.

The present application is also related to U.S. patent application Ser.No. 12/892,424 filed on Sep. 28, 2010 and entitled “Providing DigitalData Services in Optical Fiber-Based Distributed Radio Frequency (RF)Communications Systems, and Related Components and Methods,” nowabandoned, which is incorporated herein by reference in its entirety.This application is also related to U.S. Pat. Nos. 9,042,732 and9,270,374, and U.S. application Ser. No. 15/049,913, filed Feb. 22,2016.

The present application is also related to U.S. Provisional ApplicationNo. 61/230,463 filed on Jul. 31, 2009 and entitled “Optical Fiber-BasedDistributed Antenna Systems, Components, and Related Methods forCalibration Thereof,” which is incorporated herein by reference in itsentirety. This application is also related to U.S. Pat. Nos. 8,532,492and 9,112,611.

The present application is also related to U.S. Provisional ApplicationNo. 61/230,472 filed on Jul. 31, 2009 and entitled “Optical Fiber-BasedDistributed Antenna Systems, Components, and Related Methods forMonitoring the Status Thereof,” which is incorporated herein byreference in its entirety.

BACKGROUND

Field of the Disclosure

The technology of the disclosure relates to power management in remoteantenna units in distributed antenna systems for distributing radiofrequency (RF) signals to the remote antenna units.

Technical Background

Wireless communication is rapidly growing, with ever-increasing demandsfor high-speed mobile data communication. As an example, so-called“wireless fidelity” or “WiFi” systems and wireless local area networks(WLANs) are being deployed in many different types of areas (e.g.,coffee shops, airports, libraries, etc.). Distributed antenna systemscommunicate with wireless devices called “clients,” which must residewithin the wireless range or “cell coverage area” in order tocommunicate with an access point device.

One approach to deploying a distributed antenna system involves the useof radio frequency (RF) antenna coverage areas, also referred to as“antenna coverage areas.” The antenna coverage areas are provided byremote antenna units in the distributed antenna system. Remote antennaunits can provide antenna coverage areas having radii in the range froma few meters up to twenty (20) meters as an example. If the antennacoverage areas provided each cover a small area, there are typicallyonly a few users (clients) per antenna coverage area. This allows forminimizing the amount of RF bandwidth shared among the wireless systemusers. It may be desirable to provide antenna coverage areas in abuilding or other facility to provide indoor distributed antenna systemaccess to clients within the building or facility. It may also bedesirable to employ optical fiber to distribute RF communicationssignals to provide an optical fiber-based distributed antenna system.Distribution of RF communications signals over optical fiber can includeRadio-over-Fiber (RoF) distribution. Benefits of optical fiber includeincreased bandwidth.

Remote antenna units may contain power-consuming circuits and othercomponents that are involved in processing RF communications signals.For example, remote antenna units provided in an optical-fiber baseddistributed antenna system may include electrical-to-optical (E/O)converters and optical-to-electrical (O/E) converters that require powerto operate. The E/O and O/E converters convert downlink optical RFcommunications signals to downlink electrical RF communications signalsand uplink electrical RF communications signals to uplink optical RFcommunications signals, respectively. Other power-consuming componentsmay be included in the remote antenna unit. A local power source can beprovided at the remote antenna units to supply power to power-consumingcomponents in the remote antenna units. Alternatively, to avoidproviding a local power source, a remote power source can be providedthat provides power over power lines routed to the remote antenna units.The power lines may be provided in separate cabling or bundled in ahybrid cable with communications lines routed to the remote antennaunits.

It is important that a sufficient amount of power be provided to theremote antenna unit to properly power the power-consuming componentsprovided therein. Otherwise, the power-consuming components in theremote antenna unit may not properly operate and may not provideintended services for the distributed antenna system. In the case ofmultiple power-consuming components provided in a remote antenna unit,power provided to the remote antenna unit is split among the multiplecomponents. In this case, it is also important that the power be managedto sufficiently power each of the power-consuming components.

SUMMARY OF THE DETAILED DESCRIPTION

Embodiments disclosed in the detailed description include powermanagement for a remote antenna unit(s) (RAUs) in a distributed antennasystem, and related devices, systems, methods, and computer-readablemedia. The distributed antenna system may distribute radio frequency(RF) communications signals to RAUs for communicating to client devices.As a non-limiting example, the distributed antenna system may be anoptical fiber-based distributed antenna system. Power can be managed foran RAU configured to power modules and devices that may require morepower to operate than power available to the RAU. For example, the RAUmay be configured to include power-consuming RAU modules to providedistributed antenna system-related services. As another example, the RAUmay be configured to provide power to external power-consuming devicesthrough powered ports in the RAU. Depending on the configuration of theRAU, the power-consuming RAU modules and/or external power-consumingdevices may demand more power than is available at the RAU. In thisinstance, the power available at the RAU can be distributed to thepower-consuming modules and devices based on the priority of servicesdesired to be provided by the RAU.

In one embodiment, a power management device for remotely managing powerconsumed at an RAU in a distributed antenna system is provided. Thepower management device comprises a remote controller communicativelycoupled to at least one RAU configured to provide power to at least oneexternal power-consuming device connected to the at least one poweredport. The remote controller is configured to communicate with the atleast one RAU to determine an available power budget for the at leastone powered port. The remote controller is also configured tocommunicate the available power budget for the at least one powered portin the at least one RAU to the at least one RAU.

In another embodiment, a method of remotely managing power consumed atan RAU in a distributed antenna system is provided. The method includescommunicating with at least one RAU configured to provide power to atleast one external power-consuming device connected to the at least onepowered port to determine an available power budget for the at least onepowered port. The method also includes communicating the available powerbudget for the at least one powered port in the at least one RAU to theat least one RAU.

In another embodiment, a computer-readable medium is provided. Thecomputer-readable medium stores one or more programs, the one or moreprograms comprising instructions, which when executed by a remotecontroller in a distributed antenna system and remotely located from anRAU, cause the remote controller to communicate with at least one RAUprovided in a distributed antenna system to determine an available powerbudget for at least one powered port and provided in the at least oneRAU configured to provide power to at least one external power-consumingdevice connected to the at least one powered port. The instructionsfurther cause the remote controller to communicate the available powerbudget for the at least one powered port in the at least one RAU to theat least one RAU.

In another embodiment, an RAU for a distributed antenna system isprovided. The RAU comprises at least one power-consuming RAU module. Asnon-limiting examples, the at least one power-consuming RAU module maybe comprised of at least one of an RF communications module configuredto provide RF communications services, and a digital data services (DDS)module configured to provide DDS. The RAU further comprises at least onepowered port configured to provide power to at least one externalpower-consuming device connected to the at least one powered port. TheRAU further comprises a controller configured to receive an availablepower budget for the at least one powered port from a remote controllerin a distributed antenna system. The RAU controller is furtherconfigured to enable power for the at least one powered port if theavailable power budget is sufficient to power the at least one externalpower-consuming device connected to the at least one powered port.

In another embodiment, a method of managing power consumed at an RAU ina distributed antenna system is provided. The method comprises receivingan available power budget for at least one powered port configured toprovide power to at least one external power-consuming device connectedto the at least one powered port based on power required by at least onepower-consuming RAU module. As non-limiting examples, the at least onepower-consuming RAU module may be comprised of at least one of an RFcommunications module configured to provide RF communications services,and a digital data services (DDS) module configured to provide DDS. Themethod further comprises enabling power for the at least one poweredport if an available power budget is sufficient to power the at leastone external power-consuming device connected to the at least onepowered port.

In another embodiment, a computer-readable medium is provided. Thecomputer-readable medium stores one or more programs, the one or moreprograms comprising instructions, which when executed by an RAUcontroller in at least one RAU provided in a distributed antenna system,cause the RAU controller to receive an available power budget from aremote controller for at least one powered port in an RAU provided in adistributed antenna system, the RAU configured to provide power to atleast one external power-consuming device connected to the at least onepowered port based on power required by at least one power-consuming RAUmodule. The instructions further cause the RAU controller to enablepower for the at least one powered port if an available power budget issufficient to power the at least one external power-consuming deviceconnected to the at least one powered port.

It is to be understood that both the foregoing general description andthe following detailed description present embodiments, and are intendedto provide an overview or framework for understanding the nature andcharacter of the disclosure.

The accompanying drawings are included to provide a furtherunderstanding, and are incorporated into and constitute a part of thisspecification. The drawings illustrate various embodiments, and togetherwith the description serve to explain the principles and operation ofthe concepts disclosed.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic diagram of an exemplary distributed antennasystem;

FIG. 2 is a more detailed schematic diagram of exemplary head-endequipment and a remote antenna unit (RAU) that can be deployed in thedistributed antenna system of FIG. 1;

FIG. 3 is a partially schematic cut-away diagram of an exemplarybuilding infrastructure in which the distributed antenna system in FIG.1 can be employed;

FIG. 4 is a schematic diagram of another exemplary distributed antennasystem;

FIG. 5 is a schematic diagram of an exemplary embodiment of providingdigital data services to RAUs in a distributed antenna system;

FIG. 6 is a schematic diagram of an exemplary RAU configured withpower-consuming components for providing radio frequency (RF)communications services, digital data services, external power todigital data service devices, and a remote expansion unit;

FIG. 7 is an exemplary priority scheme for providing power topower-consuming components that may be present in an RAU;

FIG. 8 is a schematic diagram of an exemplary RAU that includes remotepower management for managing power provided to internal power-consumingmodules and external power-consuming modules connected to the RAU;

FIG. 9 is a flowchart illustrating an exemplary remote power managementprocess provided by the controller in FIG. 8 to remotely manage power atthe RAU;

FIG. 10 is a flowchart illustrating an exemplary power managementprocess provided by the RAU to manage power at the RAU at initializationand when configuration changes are made to the RAU;

FIG. 11 is a flowchart illustrating an exemplary power managementprocess provided by the RAU to manage power provided to powered portsprovided in an RAU;

FIG. 12 is an exemplary digital data services (DDS) module that can beprovided in the RAU to provide digital data services at the RAU; and

FIG. 13 is a schematic diagram of a generalized representation of anexemplary computer system that can be included in a head-end controller(HEC), which is adapted to execute instructions from an exemplarycomputer-readable medium to perform the power management functions inthe RAU.

DETAILED DESCRIPTION

Reference will now be made in detail to the embodiments, examples ofwhich are illustrated in the accompanying drawings, in which some, butnot all embodiments are shown. Indeed, the concepts may be embodied inmany different forms and should not be construed as limiting herein;rather, these embodiments are provided so that this disclosure willsatisfy applicable legal requirements. Whenever possible, like referencenumbers will be used to refer to like components or parts.

Embodiments disclosed in the detailed description include powermanagement for a remote antenna unit(s) (RAUs) in a distributed antennasystem, and related devices, systems, methods, and computer-readablemedia. The distributed antenna system may distribute radio frequency(RF) communications signals to RAUs for communicating to client devices.As a non-limiting example, the distributed antenna system may be anoptical fiber-based distributed antenna system. Power can be managed foran RAU configured to power modules and devices that may require morepower to operate than power available to the RAU. For example, the RAUmay be configured to include power-consuming RAU modules to providedistributed antenna system related services. As another example, the RAUmay be configured to provide power to external power-consuming devicesthrough powered ports in the RAU. Depending on the configuration of theRAU, the power-consuming RAU modules and/or external power-consumingdevices may demand more power than is available at the RAU. In thisinstance, the power available at the RAU can be distributed to thepower-consuming modules and devices based on the priority of servicesdesired to be provided by the RAU.

Before discussing power management for RAUs provided in distributedantenna systems and related components and methods starting at FIG. 5,FIGS. 1-4 are provided and first discussed below. FIGS. 1-4 provideexamples of distributed antenna systems, including those according tothe embodiments described herein.

FIG. 1 is a schematic diagram of an exemplary distributed antennasystem. In this embodiment, the distributed antenna system is an opticalfiber-based distributed antenna system 10; however, other types ofdistributed antenna systems are also possible. The optical fiber-baseddistributed antenna system 10 is configured to create one or moreantenna coverage areas for establishing communications with wirelessclient devices located in the RF range of the antenna coverage areas.The optical fiber-based distributed antenna system 10 provides RFcommunications services (e.g., cellular services). In this embodiment,the optical fiber-based distributed antenna system 10 includes head-endequipment in the form of a head-end unit (HEU) 12, one or more remoteantenna units (RAUs) 14, and an optical fiber 16 that optically couplesthe HEU 12 to the RAU 14. The HEU 12 is configured to receivecommunications over downlink electrical RF communications signals 18Dfrom a source or sources, such as a network or carrier as examples, andprovide such communications to the RAU 14. The HEU 12 is also configuredto return communications received from the RAU 14, via uplink electricalRF communications signals 18U, back to the source or sources. In thisregard in this embodiment, the optical fiber 16 includes at least onedownlink optical fiber 16D to carry signals communicated from the HEU 12to the RAU 14 and at least one uplink optical fiber 16U to carry signalscommunicated from the RAU 14 back to the HEU 12.

The optical fiber-based distributed antenna system 10 has an antennacoverage area 20 that can be substantially centered about the RAU 14.The antenna coverage area 20 of the RAU 14 forms an RF coverage area 21.The HEU 12 is adapted to perform or to facilitate any one of a number ofRadio-over-Fiber (RoF) applications, such as radio frequencyidentification (RFID), wireless local-area network (WLAN) communication,or cellular phone service. Shown within the antenna coverage area 20 isa client device 24 in the form of a mobile device as an example, whichmay be a cellular telephone as an example. The client device 24 can beany device that is capable of receiving RF communications signals. Theclient device 24 includes an antenna 26 (e.g., a wireless card) adaptedto receive and/or send electromagnetic RF communications signals.

With continuing reference to FIG. 1, to communicate the electrical RFcommunications signals over the downlink optical fiber 16D to the RAU14, to in turn be communicated to the client device 24 in the antennacoverage area 20 formed by the RAU 14, the HEU 12 includes anelectrical-to-optical (E/O) converter 28. The E/O converter 28 convertsthe downlink electrical RF communications signals 18D to downlinkoptical RF communications signals 22D to be communicated over thedownlink optical fiber 16D. The RAU 14 includes an optical-to-electrical(O/E) converter 30 to convert received downlink optical RFcommunications signals 22D back to electrical RF communications signalsto be communicated wirelessly through an antenna 32 of the RAU 14 toclient devices 24 located in the antenna coverage area 20.

Similarly, the antenna 32 is also configured to receive wireless RFcommunications from client devices 24 in the antenna coverage area 20.In this regard, the antenna 32 receives wireless RF communications fromclient devices 24 and communicates electrical RF communications signalsrepresenting the wireless RF communications to an E/O converter 34 inthe RAU 14. The E/O converter 34 converts the electrical RFcommunications signals into uplink optical RF communications signals 22Uto be communicated over the uplink optical fiber 16U. An O/E converter36 provided in the HEU 12 converts the uplink optical RF communicationssignals 22U into uplink electrical RF communications signals, which canthen be communicated as uplink electrical RF communications signals 18Uback to a network or other source. The HEU 12 in this embodiment is notable to distinguish the location of the client device 24 in thisembodiment. The client device 24 could be in the range of any antennacoverage area 20 formed by an RAU 14.

FIG. 2 is a more detailed schematic diagram of the exemplary opticalfiber-based distributed antenna system 10 of FIG. 1 that provideselectrical RF service signals for a particular RF service orapplication. In an exemplary embodiment, the HEU 12 includes a serviceunit 37 that provides electrical RF service signals by passing (orconditioning and then passing) such signals from one or more outsidenetworks 38 via a network link 39. In a particular example embodiment,this includes providing WLAN signal distribution as specified in theInstitute of Electrical and Electronics Engineers (IEEE) 802.11standard, i.e., in the frequency range from 2.4 to 2.5 GigaHertz (GHz)and from 5.0 to 6.0 GHz. Any other electrical RF communications signalfrequencies are possible. In another exemplary embodiment, the serviceunit 37 provides electrical RF service signals by generating the signalsdirectly. In another exemplary embodiment, the service unit 37coordinates the delivery of the electrical RF service signals betweenclient devices 24 within the antenna coverage area 20.

With continuing reference to FIG. 2, the service unit 37 is electricallycoupled to the E/O converter 28 that receives the downlink electrical RFcommunications signals 18D from the service unit 37 and converts them tocorresponding downlink optical RF communications signals 22D. In anexemplary embodiment, the E/O converter 28 includes a laser suitable fordelivering sufficient dynamic range for the RoF applications describedherein, and optionally includes a laser driver/amplifier electricallycoupled to the laser. Examples of suitable lasers for the E/O converter28 include, but are not limited to, laser diodes, distributed feedback(DFB) lasers, Fabry-Perot (FP) lasers, and vertical cavity surfaceemitting lasers (VCSELs).

With continuing reference to FIG. 2, the HEU 12 also includes the O/Econverter 36, which is electrically coupled to the service unit 37. TheO/E converter 36 receives the uplink optical RF communications signals22U and converts them to corresponding uplink electrical RFcommunications signals 18U. In an example embodiment, the O/E converter36 is a photodetector, or a photodetector electrically coupled to alinear amplifier. The E/O converter 28 and the O/E converter 36constitute a “converter pair” 35, as illustrated in FIG. 2.

In accordance with an exemplary embodiment, the service unit 37 in theHEU 12 can include an RF communications signal conditioner unit 40 forconditioning the downlink electrical RF communications signals 18D andthe uplink electrical RF communications signals 18U, respectively. Theservice unit 37 can include a digital signal processing unit (“digitalsignal processor”) 42 for providing to the RF communications signalconditioner unit 40 an electrical signal that is modulated onto an RFcarrier to generate a desired downlink electrical RF communicationssignal 18D. The digital signal processor 42 is also configured toprocess a demodulation signal provided by the demodulation of the uplinkelectrical RF communications signal 18U by the RF communications signalconditioner unit 40. The service unit 37 in the HEU 12 can also includean optional head-end unit controller (HEC) 44 (or “controller 44”) forprocessing data and otherwise performing logic and computing operations,and a memory unit 46 for storing data, such as data to be transmittedover a WLAN or other network for example.

With continuing reference to FIG. 2, the RAU 14 also includes aconverter pair 48 comprising the O/E converter 30 and the E/O converter34. The O/E converter 30 converts the received downlink optical RFcommunications signals 22D from the HEU 12 back into downlink electricalRF communications signals 50D. The E/O converter 34 converts uplinkelectrical RF communications signals 50U received from the client device24 into the uplink optical RF communications signals 22U to becommunicated to the HEU 12. The O/E converter 30 and the E/O converter34 are electrically coupled to the antenna 32 via an RF signal-directingelement 52, such as a circulator for example. The RF signal-directingelement 52 serves to direct the downlink electrical RF communicationssignals 50D and the uplink electrical RF communications signals 50U, asdiscussed below. In accordance with an exemplary embodiment, the antenna32 can include any type of antenna, including but not limited to one ormore patch antennas, such as disclosed in U.S. patent application Ser.No. 11/504,999, now U.S. Pat. No. 7,627,250, filed Aug. 16, 2006,entitled “Radio-over-Fiber Transponder With A Dual-Band Patch AntennaSystem,” and U.S. patent application Ser. No. 11/451,553, filed Jun. 12,2006, entitled “Centralized Optical Fiber-based Wireless PicocellularSystems and Methods,” both of which are incorporated herein by referencein their entireties.

With continuing reference to FIG. 2, the optical fiber-based distributedantenna system 10 also includes a power supply 54 that provides anelectrical power signal 56. The power supply 54 is electrically coupledto the HEU 12 for powering the power-consuming elements therein. In anexemplary embodiment, an electrical power line 58 runs through the HEU12 and over to the RAU 14 to power the O/E converter 30 and the E/Oconverter 34 in the converter pair 48, the optional RF signal-directingelement 52 (unless the RF signal-directing element 52 is a passivedevice such as a circulator for example), and any other power-consumingelements provided. In an exemplary embodiment, the electrical power line58 includes two wires 60 and 62 that carry a single voltage and that areelectrically coupled to a DC power converter 64 at the RAU 14. The DCpower converter 64 is electrically coupled to the O/E converter 30 andthe E/O converter 34 in the converter pair 48, and changes the voltageor levels of the electrical power signal 56 to the power level(s)required by the power-consuming components in the RAU 14. In anexemplary embodiment, the DC power converter 64 is either a DC/DC powerconverter or an AC/DC power converter, depending on the type ofelectrical power signal 56 carried by the electrical power line 58. Inanother example embodiment, the electrical power line 58 (dashed line)runs directly from the power supply 54 to the RAU 14 rather than from orthrough the HEU 12. In another example embodiment, the electrical powerline 58 includes more than two wires and may carry multiple voltages.

To provide further exemplary illustration of how an optical fiber-baseddistributed antenna system can be deployed indoors, FIG. 3 is provided.FIG. 3 is a partially schematic cut-away diagram of a buildinginfrastructure 70 employing an optical fiber-based distributed antennasystem. The system may be the optical fiber-based distributed antennasystem 10 of FIGS. 1 and 2. The building infrastructure 70 generallyrepresents any type of building in which the optical fiber-baseddistributed antenna system 10 can be deployed. As previously discussedwith regard to FIGS. 1 and 2, the optical fiber-based distributedantenna system 10 incorporates the HEU 12 to provide various types ofcommunications services to coverage areas within the buildinginfrastructure 70, as an example. For example, as discussed in moredetail below, the optical fiber-based distributed antenna system 10 inthis embodiment is configured to receive wireless RF communicationssignals and convert the RF communications signals into RoF signals to becommunicated over the optical fiber 16 to multiple RAUs 14. The opticalfiber-based distributed antenna system 10 in this embodiment can be, forexample, an indoor distributed antenna system (IDAS) to provide wirelessservice inside the building infrastructure 70. These wireless signalscan include cellular service, wireless services such as RFID tracking,Wireless Fidelity (WiFi), local area network (LAN), WLAN, andcombinations thereof, as examples.

With continuing reference to FIG. 3, the building infrastructure 70 inthis embodiment includes a first (ground) floor 72, a second floor 74,and a third floor 76. The floors 72, 74, 76 are serviced by the HEU 12through a main distribution frame 78 to provide antenna coverage areas80 in the building infrastructure 70. Only the ceilings of the floors72, 74, 76 are shown in FIG. 3 for simplicity of illustration. In theexample embodiment, a main cable 82 has a number of different sectionsthat facilitate the placement of a large number of RAUs 14 in thebuilding infrastructure 70. Each RAU 14 in turn services its owncoverage area in the antenna coverage areas 80. The main cable 82 caninclude, for example, a riser cable 84 that carries all of the downlinkand uplink optical fibers 16D, 16U to and from the HEU 12. The risercable 84 may be routed through an interconnect unit (ICU) 85. The ICU 85may be provided as part of or separate from the power supply 54 in FIG.2. The ICU 85 may also be configured to provide power to the RAUs 14 viathe electrical power line 58, as illustrated in FIG. 2 and discussedabove, provided inside an array cable 87, or tail cable or home-runtether cable as other examples, and distributed with the downlink anduplink optical fibers 16D, 16U to the RAUs 14. The main cable 82 caninclude one or more multi-cable (MC) connectors adapted to connectselect downlink and uplink optical fibers 16D, 16U, along with anelectrical power line, to a number of optical fiber cables 86.

The main cable 82 enables the multiple optical fiber cables 86 to bedistributed throughout the building infrastructure 70 (e.g., fixed tothe ceilings or other support surfaces of each floor 72, 74, 76) toprovide the antenna coverage areas 80 for the first, second, and thirdfloors 72, 74, and 76. In an example embodiment, the HEU 12 is locatedwithin the building infrastructure 70 (e.g., in a closet or controlroom), while in another example embodiment, the HEU 12 may be locatedoutside of the building infrastructure 70 at a remote location. A basetransceiver station (BTS) 88, which may be provided by a second partysuch as a cellular service provider, is connected to the HEU 12, and canbe co-located or located remotely from the HEU 12. A BTS is any stationor source that provides an input signal to the HEU 12 and can receive areturn signal from the HEU 12. In a typical cellular system, forexample, a plurality of BTSs are deployed at a plurality of remotelocations to provide wireless telephone coverage. Each BTS serves acorresponding cell, and when a mobile client device enters the cell, theBTS communicates with the mobile client device. Each BTS can include atleast one radio transceiver for enabling communication with one or moresubscriber units operating within the associated cell. As anotherexample, wireless repeaters or bi-directional amplifiers could also beused to serve a corresponding cell in lieu of a BTS. Alternatively,radio input could be provided by a repeater or picocell as otherexamples.

The optical fiber-based distributed antenna system 10 in FIGS. 1-3 anddescribed above provides point-to-point communications between the HEU12 and the RAU 14. Each RAU 14 communicates with the HEU 12 over adistinct downlink and uplink optical fiber pair to provide thepoint-to-point communications. Whenever an RAU 14 is installed in theoptical fiber-based distributed antenna system 10, the RAU 14 isconnected to a distinct downlink and uplink optical fiber pair connectedto the HEU 12. The downlink and uplink optical fibers 16U, 16D may beprovided in a fiber optic cable. Multiple downlink and uplink opticalfiber pairs can be provided in a fiber optic cable to service multipleRAUs 14 from a common fiber optic cable. For example, with reference toFIG. 3, RAUs 14 installed on a given floor 72, 74, or 76 may be servicedfrom the same optical fiber 16. In this regard, the optical fiber 16 mayhave multiple nodes where distinct downlink and uplink optical fiberpairs can be connected to a given RAU 14. One downlink optical fiber 16could be provided to support multiple channels each usingwavelength-division multiplexing (WDM), as discussed in U.S. patentapplication Ser. No. 12/892,424 entitled “Providing Digital DataServices in Optical Fiber-Based Distributed Radio Frequency (RF)Communications Systems, and Related Components and Methods,”incorporated herein by reference in its entirety. Other options for WDMand frequency-division multiplexing (FDM) are also disclosed in U.S.patent application Ser. No. 12/892,424, any of which can be employed inany of the embodiments disclosed herein.

FIG. 4 is a schematic diagram of another exemplary distributed antennasystem 90. In this embodiment, the distributed antenna system 90 is anoptical fiber-based distributed antenna system comprised of three maincomponents. One or more radio interfaces provided in the form of radiointerface modules (RIMs) 92(1)-92(M) in this embodiment are provided inan HEU 94 to receive and process downlink electrical RF communicationssignals 96(1)-96(R) prior to optical conversion into downlink optical RFcommunications signals. The processing of the downlink electrical RFcommunications signals 96(1)-96(R) can include any of the processingpreviously described above in the HEU 12 in FIG. 2. The notations “1-R”and “1-M” indicate that any number of the referenced component, 1-R and1-M, respectively, may be provided. As will be described in more detailbelow, the HEU 94 is configured to accept a plurality of RIMs92(1)-92(M) as modular components that can easily be installed andremoved or replaced in the HEU 94. In one embodiment, the HEU 94 isconfigured to support up to four (4) RIMs 92(1)-92(M) as an example.

Each RIM 92(1)-92(M) can be designed to support a particular type ofradio source or range of radio sources (i.e., frequencies) to provideflexibility in configuring the HEU 94 and the optical fiber-baseddistributed antenna system 90 to support the desired radio sources. Forexample, one RIM 92 may be configured to support the PersonalCommunication Services (PCS) radio band. Another RIM 92 may beconfigured to support the 700 MHz radio band. In this example, byinclusion of these RIMs 92, the HEU 94 would be configured to supportand distribute RF communications signals on both PCS and LTE 700 radiobands. RIMs 92 may be provided in the HEU 94 that support any frequencybands desired, including but not limited to US Cellular band, PCS(Personal Communication Services) ban, AWS (Advanced Wireless Services)band, 700 MHz band, Global System for Mobile communications (GSM) 900,GSM 1800, UMTS. RIMs 92 may be provided in the HEU 94 that support anywireless technologies desired, including but not limited to CDMA (CodeDivision Multiple Access), CDMA200, 1×RTT, EV-DO (Evolution—Data Only),UMTS (Universal Mobile Telecommunication System), HSPA (High-speedPacket Access), GSM, GPRS (General Packet Radio Services), EDGE(Enhanced Data GSM Environment), TDMA (Time Division Multiple Access),LTE (Long Term Evolution), iDEN, and CDPD (Cellular Digital PacketData).

RIMs 92 may be provided in the HEU 94 that support any frequenciesdesired, including but not limited to US FCC and Industry Canadafrequencies (824-849 MHz on uplink and 869-894 MHz on downlink), US FCCand Industry Canada frequencies (1850-1915 MHz on uplink and 1930-1995MHz on downlink), US FCC and Industry Canada frequencies (1710-1755 MHzon uplink and 2110-2155 MHz on downlink), US FCC frequencies (698-716MHz and 776-787 MHz on uplink and 728-746 MHz on downlink). EU R & TTEfrequencies (880-915 MHz on uplink and 925-960 MHz on downlink), EU R &TTE frequencies (1710-1785 MHz on uplink and 1805-1880 MHz on downlink),EU R & TTE frequencies (1920-1980 MHz on uplink and 2110-2170 MHz ondownlink), US FCC frequencies (806-824 MHz on uplink and 851-869 MHz ondownlink), US FCC frequencies (896-901 MHz on uplink and 929-941 MHz ondownlink), US FCC frequencies (793-805 MHz on uplink and 763-775 MHz ondownlink), and US FCC frequencies (2495-2690 MHz on uplink anddownlink).

The downlink electrical RF communications signals 96(1)-96(R) areprovided to a plurality of optical interfaces provided in the form ofoptical interface modules (OIMs) 98(1)-98(N) in this embodiment toconvert the downlink electrical RF communications signals 96(1)-96(N)into downlink optical signals 100(1)-100(R). The notation “1-N”indicates that any number of the referenced component 1-N may beprovided. The OIMs 98 may be configured to provide one or more opticalinterface components (OICs) that contain O/E and E/O converters, as willbe described in more detail below. The OIMs 98 support the radio bandsthat can be provided by the RIMs 92, including the examples previouslydescribed above. Thus, in this embodiment, the OIMs 98 may support aradio band range from 400 MHz to 2700 MHz, as an example, so providingdifferent types or models of OIMs 98 for narrower radio bands to supportpossibilities for different radio band-supported RIMs 92 provided in theHEU 94 is not required. Further, as an example, the OIMs 98s may beoptimized for sub-bands within the 400 MHz to 2700 MHz frequency range,such as 400-700 MHz, 700 MHz-1 GHz, 1 GHz-1.6 GHz, and 1.6 GHz-2.7 GHz,as examples.

The OIMs 98(1)-98(N) each include E/O converters to convert the downlinkelectrical RF communications signals 96(1)-96(R) to downlink opticalsignals 100(1)-100(R). The downlink optical signals 100(1)-100(R) arecommunicated over downlink optical fiber(s) 103D to a plurality of RAUs102(1)-102(P). The notation “1-P” indicates that any number of thereferenced component 1-P may be provided. O/E converters provided in theRAUs 102(1)-102(P) convert the downlink optical signals 100(1)-100(R)back into downlink electrical RF communications signals 96(1)-96(R),which are provided over links 104(1)-104(P) coupled to antennas106(1)-106(P) in the RAUs 102(1)-102(P) to client devices in thereception range of the antennas 106(1)-106(P).

E/O converters are also provided in the RAUs 102(1)-102(P) to convertuplink electrical RF communications signals received from client devicesthrough the antennas 106(1)-106(P) into uplink optical signals108(1)-108(R) to be communicated over uplink optical fibers 103U to theOIMs 98(1)-98(N). The OIMs 98(1)-98(N) include O/E converters thatconvert the uplink optical signals 108(1)-108(R) into uplink electricalRF communications signals 110(1)-110(R) that are processed by the RIMs92(1)-102(M) and provided as uplink electrical RF communications signals112(1)-112(R).

It may be desirable to provide both digital data services and RFcommunications services for client devices. For example, it may bedesirable to provide digital data services and RF communicationsservices in the building infrastructure 70 (FIG. 3) to client deviceslocated therein. Wired and wireless devices may be located in thebuilding infrastructure 70 that are configured to access digital dataservices. Examples of digital data services include, but are not limitedto, Ethernet, WLAN, WiMax, WiFi, Digital Subscriber Line (DSL), and LTE,etc. Ethernet standards could be supported, including but not limited to100 Megabits per second (Mbs) (i.e., fast Ethernet) or Gigabit (Gb)Ethernet, or ten Gigabit (10G) Ethernet. Examples of digital datadevices include, but are not limited to, wired and wireless servers,wireless access points (WAPs), gateways, desktop computers, hubs,switches, remote radio heads (RRHs), baseband units (BBUs), andfemtocells. A separate digital data services network can be provided toprovide digital data services to digital data devices.

FIG. 5 is a schematic diagram of an exemplary embodiment of providingdigital data services over separate downlink and uplink optical fibersfrom RF communications services to RAUs in an optical fiber-baseddistributed antenna system 120. The optical fiber-based distributedantenna system 120 is described as including some components provided inthe optical fiber-based distributed antenna system 10 of FIGS. 1-3.These common components are illustrated in FIG. 5 with common elementnumbers with FIGS. 1-3. However, note that the optical fiber-baseddistributed antenna system 120 could also employ other components,including those in the optical fiber-based distributed antenna system 90in FIG. 4.

As illustrated in FIG. 5, the HEU 12 is provided. The HEU 12 receivesthe downlink electrical RF communications signals 18D from the BTS 88.As previously discussed, the HEU 12 converts the downlink electrical RFcommunications signals 18D to downlink optical RF communications signals22D to be distributed to the RAUs 14. The HEU 12 is also configured toconvert the uplink optical RF communications signals 22U received fromthe RAUs 14 into uplink electrical RF communications signals 18U to beprovided to the BTS 88 and onto a network 122 connected to the BTS 88. Apatch panel 123 may be provided to receive the downlink and uplinkoptical fibers 16D, 16U configured to carry the downlink and uplinkoptical RF communications signals 22D, 22U. The downlink and uplinkoptical fibers 16D, 16U may be bundled together in one or more risercables 84 and provided to one or more ICUs 85, as previously discussedand illustrated in FIG. 3.

To provide digital data services in the optical fiber-based distributedantenna system 120 in this embodiment, a digital data servicescontroller (also referred to as “DDS controller”) 124 in the form of amedia converter in this example is provided. The DDS controller 124 caninclude only a media converter for provision media conversionfunctionality or can include additional functionality to facilitatedigital data services. The DDS controller 124 is configured to providedigital data services over a communications link, interface, or othercommunications channel or line, which may be either wired, wireless, ora combination of both. The DDS controller 124 may include a housingconfigured to house digital media converters (DMCs) 126 to interface toa DDS switch 127 to support and provide digital data services. Forexample, the DDS switch 127 could be an Ethernet switch. The DDS switch127 may be configured to provide Gigabit (Gb) Ethernet digital dataservice as an example. The DMCs 126 are configured to convert electricaldigital signals to optical digital signals, and vice versa. The DMCs 126may be configured for plug and play installation (i.e., installation andoperability without user configuration required) into the DDS controller124. For example, the DMCs 126 may include Ethernet input connectors oradapters (e.g., RJ-45) and optical fiber output connectors or adapters(e.g., LC, SC, ST, MTP).

With continuing reference to FIG. 5, the DDS controller 124 (via theDMCs 126) in this embodiment is configured to convert downlinkelectrical digital signals (or downlink electrical digital data servicessignals) 128D over digital line cables 129 from the DDS switch 127 intodownlink optical digital signals (or downlink optical digital dataservices signals) 130D that can be communicated over downlink opticalfiber 135D to RAUs 14. The DDS controller 124 (via the DMCs 126) is alsoconfigured to receive uplink optical digital signals 130U from the RAUs14 via the uplink optical fiber 135U and convert the uplink opticaldigital signals 130U into uplink electrical digital signals 128U to becommunicated to the DDS switch 127. In this manner, the digital dataservices can be provided over optical fiber as part of the opticalfiber-based distributed antenna system 120 to provide digital dataservices in addition to RF communication services. Client deviceslocated at the RAUs 14 can access these digital data services and/or RFcommunications services depending on their configuration. Exemplarydigital data services include WLAN, Ethernet, WLAN, WiMax, WiFi, DigitalSubscriber Line (DSL), and LTE, etc. Ethernet standards could besupported, including but not limited to 100 Megabits per second (Mbs)(i.e., fast Ethernet) or Gigabit (Gb) Ethernet, or ten Gigabit (10G)Ethernet.

With continuing reference to FIG. 5, in this embodiment, downlink anduplink optical fibers 132D, 132U are provided in a fiber optic cable 134that is interfaced to the ICU 85. The ICU 85 provides a common point inwhich the downlink and uplink optical fibers 132D, 132U carrying digitaloptical signals can be bundled with the downlink and uplink opticalfibers 16U, 16D carrying optical RF communications signals. One or moreof the fiber optic cables 134, also referenced herein as array cables134, can be provided containing the downlink and uplink optical fibers135D, 135U for RF communications services and digital data services tobe routed and provided to the RAUs 14. Any combination of services ortypes of optical fibers can be provided in the array cable 134. Forexample, the array cable 134 may include single mode and/or multi-modeoptical fibers for RF communication services and/or digital dataservices.

Examples of ICUs that may be provided in the optical fiber-baseddistributed antenna system 120 to distribute both downlink and uplinkoptical fibers 135D, 135U for RF communications services and digitaldata services are described in U.S. patent application Ser. No.12/466,514, filed on May 15, 2009, entitled “Power Distribution Devices,Systems, and Methods For Radio-Over-Fiber (RoF) DistributedCommunication,” and U.S. Provisional Application Ser. No. 61/330,385filed on May 2, 2010, entitled “Power Distribution in OpticalFiber-Based Distributed Communications Systems Providing Digital Dataand Radio Frequency (RF) Communications Services, and Related Componentsand Methods,” both of which are incorporated herein by reference intheir entireties.

With continuing reference to FIG. 5, some RAUs 14 can be connected toaccess units (AUs) 138, which may be access points (APs) or otherdevices supporting digital data services. AUs 138 can also be connecteddirectly to the HEU 12. AUs 138 are illustrated, but the AUs 138 couldbe any other device supporting digital data services. In the example ofAUs, the AUs 138 provide access to the digital data services provided bythe DDS switch 127. This is because the downlink and uplink opticalfibers 135D, 135U carrying downlink and uplink optical digital signals130D, 130U converted from downlink and uplink electrical digital signals128D, 128U from the DDS switch 127 are provided to the AUs 138 via thearray cables 134 and RAUs 14. Digital data client devices can access theAUs 138 to access digital data services provided through the DDS switch127. The AUs 138 may also each include an antenna 140 to providewireless access to digital data services provided through the DDS switch127.

As will be described in more detail below, providing RF communicationsservices and digital data services involves providing RF communicationsmodules and DDS modules in the RAUs 14 and/or AUs 138 in the example ofFIG. 5. These modules are power-consuming modules that require power tooperate. Power distributed to the RAUs can also be used to provideaccess to power for DDS modules, as opposed to providing separate powersources for DDS modules and RF communications modules. For example,power distributed to the RAUs 14 in FIG. 5 by or through the ICUs 85 canalso be used to provide power to the AUs 138 located at the RAUs 14 inthe optical fiber-based distributed antenna system 120. In this regard,the ICUs 85 may be configured to provide power for both RAUs 14 and theAUs 138 over an electrical power line 142, as illustrated in FIG. 5. Aswill also be described in more detail below, the RAUs 14 and/or AUs 138may also be configured with powered ports to provide power to externalclient devices connected to the powered ports, such as IEEE 802.3afPower-over-Ethernet (PoE) compatible devices as an example. However,referring to FIG. 5 as an example, the power made available to the RAUs14 and AUs 138 may not be sufficient to power all of the modulesprovided and external devices connected to the RAUs 14 and AUs 138.

In this regard, embodiments disclosed below include power management foran RAU(s) in a distributed antenna system, and related devices, systems,methods, and computer-readable media. Power can be managed for an RAUconfigured to power modules and devices that may require more power tooperate than power available to the RAU. For example, the RAU may beconfigured to include power-consuming RAU modules to provide distributedantenna system-related services. As another example, the RAU may beconfigured to provide power through powered ports in the RAU to externalpower-consuming devices. Depending on the configuration of the RAU, thepower-consuming RAU modules and/or external power-consuming devices maydemand more power than is available at the RAU. In this instance, thepower available at the RAU can be distributed to the power-consumingmodules and devices based on the priority of services desired to beprovided by the RAU.

FIG. 6 is a schematic diagram of an exemplary RAU 14 configured withpower-consuming components. The RAU 14 is configured to receive powerover a power line 150 routed to the RAU 14 from either a local powersource or a remote power source to make power available forpower-consuming components associated with the RAU 14. As a non-limitingexample, the power line 150 may provide a voltage of between forty-eight(48) and sixty (60) Volts at a power rating of between eighty (80) toone hundred (100) Watts. In this example, the RAU 14 includes an RFcommunications module 152 for providing RF communications services. TheRF communications module 152 requires power to operate in thisembodiment and receives power from the power line 150. Power may berouted from the power line 150 directly to the RF communications module152, or indirectly from another module. The RF communications module 152may include any of the previously referenced components to provide RFcommunications services, including O/E and E/O conversion.

With continuing reference to FIG. 6, the RAU 14 may also include a DDSmodule 154 to provide media conversion (e.g., O/E and E/O conversions)and route digital data services received from the DDS switch 127 in FIG.5 to externally connected power-consuming devices (PDs) 156(1)-156(Q)configured to receive digital data services. Power may be routed fromthe power line 150 to the DDS module 154 through the RF communicationsmodule 152 as one example. is provided to route power from the powerline 150 to the DDS module 154. With reference to FIG. 6, the digitaldata services are routed by the DDS module 154 through communicationsports 158(1)-158(Q) provided in the RAU 14. As a non-limiting example,the communications ports 158(1)-158(Q) may be RJ-45 connectors. Thecommunications ports 158(1)-158(Q) may be powered, meaning that aportion of the power from the power line 150 is provided to the poweredcommunications ports 158(1)-158(Q). In this manner, PDs 156(1)-156(Q)configured to receive power through a powered communications port 158can be powered from power provided to the RAU 14 when connected to thepowered communications port 158. In this manner, a separate power sourceis not required to power the PDs 156(1)-156(Q). For example, the DDSmodule 154 may be configured to route power to the poweredcommunications ports 158(1)-158(Q) as described in the PoE standard.

With continuing reference to FIG. 6, one or more remote expansion units(RXUs) 160(1)-160(Z) may also be connected to the RAU 14. The RXUs160(1)-160(Z) can be provided to provide additional RF communicationsservices through the RAU 14, but remotely from the RAU 14. For example,if additional RF communications bands are needed and there are noadditional bands available in a distributed antenna system, the RFcommunications bands of an existing RAU 14 can be expanded withoutadditional communications bands by providing the RXUs 160(1)-160(Z). TheRXUs 160(1)-160(Z) are connected to the distributed antenna systemthrough the RAU 14. The RXUs 160(1)-160(Z) can include the same orsimilar components provided in the RF communications module 152 toreceive downlink RF communications signals 162D and to provide receiveduplink RF communications signals 162U from client devices to thedistributed antenna system through the RAU 14. The RXUs 160(1)-160(Z)are also power-consuming modules, and thus in this embodiment, powerfrom the power line 150 is routed by the RAU 14 to the RXUs160(1)-160(Z) over a power line 164.

The power provided on the power line 150 in FIG. 6 may not be sufficientto provide power for the modules 152, 154, 160(1)-160(Z) and externalPDs 156(1)-156(Q) provided in the RAU 14. For example, eighty (80) Wattsof power may be provided on the power line 150 in FIG. 6. However, theRF communications module 152 may consume thirty (30) Watts of power, theRXUs 160(1)-160(Z) may consume twenty (20) Watts of power, and the DDSmodule 154 may consume five (5) Watts of power. This is a total offifty-five (55) Watts. In this example, twenty-five (25) Watts areavailable to be shared among the powered communications ports158(1)-158(Q). However, the PDs 156(1)-156(Q) may be configured torequire more power than twenty-five (25) Watts. For example, if the PDs156(1)-156(Q) are configured according to the PoE standard, power sourceequipment (PSE) provided in the RAU 14 to provide power to the poweredcommunications ports 158(1)-158(Q) may be required to provide up to 15.4Watts of power to each powered communications port 158(1)-158(Q). Inthis example, if more than one powered communications port 158(1)-158(Q)is provided, there will not be sufficient power to power each of thepowered communications port 158(1)-158(Q) at 30 Watts (i.e., a PoE Class4 device).

Thus, to ensure proper operation of the maximum power consuming modules152, 154, 160(1)-160(Z) possible in an RAU 14, less power could beprovided to the powered communications port 158(1)-158(Q) or only onepowered communications port 158(1)-158(Q) could be enabled with power.However, if one of the other modules 152, 154, 160(1)-160(Z) was notpresent, sufficient power may be available to be provided to each of thepowered communications ports 158(1)-158(Q) provided. Further, if a PD156 connected to a powered communication port 158 is a lower classdevice that does not require 30 Watts of power, there may be sufficientpower available to power the PDs 156(1)-156(Q) connected to each of thepowered communications ports 158(1)-158(Q).

In this regard, FIG. 7 is an exemplary priority scheme for a powermanagement scheme to provide sufficient power to power-consuming modulesand PDs that may be powered by an RAU 14. In this example, RFcommunications services have been assigned higher priority than digitaldata services and powered ports. Thus, in this example, the availablepower on the power line 150 will be made available to the RFcommunications module 152. If more power is available from the powerline 150 after power has been budgeted for the RF communications module152, the remaining power is made available to the RXUs 160(1)-160(Z) toprovide expansion RF communications services. If more power is availablefrom the power line 150 after power has been budgeted for the RFcommunications module 152 and the RXUs 160(1)-160(Z), the remainingpower is made available to the DDS module 154 to provide digital dataservices. If more power is available from the power line 150 after powerhas been budgeted for the RF communications module 152, the RXUs160(1)-160(Z), and the DDS module 154, the remaining power is madeavailable to the powered communications ports 158(1)-158(Q) to providepower to the PDs 156(1)-156(Q). Note that the priority schemed in FIG. 7is exemplary and any other priority scheme desired could be implementedin a power management scheme.

With continuing reference to FIG. 7, power is budgeted such that poweris made available sufficient to power the PD 158(1) connected to thefirst powered communications port 158(1). If more power is availablefrom the power line 150 after power has been budgeted for the RFcommunications module 152, the RXUs 160(1)-160(Z), the DDS module 154,and the PD 158(1) connected to the first powered communications port158(1), power is made available to the other powered communicationsports 158(2)-158(Q) until sufficient power is not available to power thePDs 156(2)-156(Q) connected to the additional powered communicationsports 158(2)-158(Q). If the remaining power budget is not sufficient topower the PDs 156 connected to any powered communications ports 158,these powered communications ports 158 can be disabled. Further, if anyof the modules 152, 154, 160(1)-160(Z) are not present or are removedfor a particular RAU 14, the available power budget for the poweredcommunications ports 158(1)-158(Q) may increase thereby allowingpreviously disabled powered communications ports 158(1)-158(Q) to beenabled.

FIG. 8 is a schematic diagram of an exemplary embodiment of componentsthat can be provided in the RAU 14 of FIG. 6 to provide for remote powermanagement of power provided to the power-consuming modules 152, 154,160(1)-160(Z) and the externally connected PDs 156(1)-156(Q). Thediscussion of remote power management of the RAU 14 in FIG. 8 will bedescribed in conjunction with the flowcharts in FIGS. 9-11. FIG. 9 is aflowchart illustrating an exemplary remote power management processprovided by the HEC 44 in FIG. 2 to perform remote power management atan RAU 14. FIG. 10 is a flowchart illustrating an exemplary powermanagement process provided by an RAU 14 to manage power at the RAU 14at initialization and when configuration changes are made to the RAU 14.FIG. 11 is a flowchart illustrating an exemplary power managementprocess provided by an RAU 14 to manage power provided to PDs156(1)-156(Q) connected to powered communications ports 158(1)-158(Q)provided in a RAU 14.

With reference to FIG. 8, the RAU 14 includes power source equipment(PSE) 170. The PSE 170 is configured to direct power from a power line171, which receives power from the power line 150 through the RFcommunications module 152, to PDs 156(1)-156(Q) connected to the poweredcommunications ports 158(1)-158(Q). A controller 176 provided in the DDSmodule 154 coupled to memory 178 is configured to provide powermanagement functions according to an available power budget receivedfrom the HEC 44, as will be described in more detail below with regardto FIGS. 9-11. By receiving the available power budget that can beprovided from the power line 150 by the PSE 170 to power the PDs156(1)-156(Q) connected to the powered communications ports158(1)-158(Q), the PSE 170 can manage directing power to the PDs156(1)-156(Q) connected to the powered communications ports158(1)-158(Q) without depriving the other modules 152, 154,160(1)-160(Z) present in the RAU 14 from receiving sufficient power tooperate.

As illustrated in FIG. 9, to provide power management at the RAUs 14,the HEC 44 in the HEU 12 is employed. For each RAU 14, the HEC 44receives a configuration of which power-consuming modules 152, 154,160(1)-160(Z) are present in the RAU 14 (block 180 in FIG. 9). The HEC44 communicates with the RAUs 14 using digital communicationscommunicated over the same communications links as provided to carry RFcommunications signals. More information on providing a digitalcommunication and control system in a distributed antenna system isdescribed in U.S. Provisional Application No. 61/230,472 filed on Jul.31, 2009 entitled “Optical Fiber-Based Distributed Antenna Systems,Components, and Related Methods for Monitoring the Status Thereof” whichis incorporated herein by reference in its entirety. The HEC 44determines the power required for the modules 152, 154, 160(1)-160(Z)present in the RAU 14 by consulting the memory unit 46 (block 182 inFIG. 9). For example, the memory unit 46 may be programmed with thepower consumption rates correlated to different types of modules 152,154, 160(1)-160(Z) that can be looked up in the memory unit 46 by theHEC 44.

As will be discussed below with regard to FIG. 10, the RAU 14 mayprovide the particular hardware and/or software elements, and/orversions of those elements of the modules 152, 154, 160(1)-160(Z)present in the RAU 14 that can be used by the HEC 44 to determine thepower requirements of the modules 152, 154, 160(1)-160(Z). The HEC 44then determines the available power budget for the RAU 14 to providepower to any PDs 156(1)-156(Q) connected to the powered communicationsports 158(1)-158(Q) based on the total power provided to the RAU 14minus the power required to sufficiently power the modules 152, 154,160(1)-160(Z) present in the RAU 14 (block 184 in FIG. 9). The totalpower available to the RAU 14 can be programmed into the memory unit 46,including by a user through a graphical user interface (GUI) hosted bythe HEU 12, or by other configuration. The process continues on arepetitive basis for each of the RAUs 14 configured for the HEU 12. Byperforming the process in FIG. 9, the RAUs 14 receive the availablepower budget that can be allocated to provide power to the PDs156(1)-156(Q) connected to the powered communications ports158(1)-158(Q) in the RAUs 14.

The RAU 14 also performs a process to provide power management. Theprocess may be performed by the controller 176 in the DDS module 154illustrated in FIG. 8. FIG. 10 is a flowchart illustrating an exemplarypower management process provided by an RAU 14 to manage power at theRAU 14 at initialization and when configuration changes are made to theRAU 14. The RAU 14 checks the configuration of the modules 152, 154,160(1)-160(Z) present in the RAU 14 to determine if the configuration ofthe RAU 14 has changed (block 190). For example, a module 152, 154,160(1)-160(Z) may have been added or removed from the RAU since theconfiguration was last determined and provided to the HEC 44. If theconfiguration of the RAU 14 has changed (block 192), the RAU 14 obtainsthe module type and the hardware and software versions of the modules152, 154, 160(1)-160(Z) (block 194). The RAU 14 then sends the moduletype and the hardware and software versions of the modules 152, 154,160(1)-160(Z) to the HEC 44 (block 196). This information is received bythe HEC 44 in block 180 in FIG. 9, previously described above.

With continuing reference to FIG. 10, the controller 176 in the RAU 14waits for the new available power budget for the RAU 14 provided by theHEC 44 according to the process in FIG. 9 (block 198). When received(block 200), the controller 174 determines if the DDS module 154 isinstalled in the RAU 14 (block 202). If not, the controller 176determines if the RXU modules 160(1)-160(Z) are installed (block 204).If not, the process repeats. If the RXU modules 160(1)-160(Z) areinstalled (block 204), the controller 176 determines if the RXU modules160(1)-160(Z) are switched on (block 206). If so, the process repeats.If not, the controller 176 instructs the RF communications module 152 toswitch on the RXU modules 160(1)-160(Z) (block 208) and the processrepeats.

With continuing reference to FIG. 10, if the controller 176 determinesthat the DDS module 154 is installed (block 202), this means thatdigital data services are provided by the RAU 14. In this instance, thepowered communications ports 158 are present to allow PDs 156(1)-156(Q)to connect to the powered communications ports 158(1)-158(Q) to receivedigital data services supported by the DDS module 154. In this regard,the controller 176 directs the PSE 170 to send the available powerbudget received from the HEC 44 to the powered communications ports158(1)-158(Q) in the RAU 14 (block 210). The PDs 156(1)-156(Q) connectedto the powered communications ports 158(1)-158(Q) may be enabled ordisabled depending on the available power budget and the powerrequirements of the PDs 156(1)-156(Q) connected to the poweredcommunications ports 158(1)-158(Q). The controller 176 waits for astatus of the PDs 156(1)-156(Q) connected to the powered communicationsports 158 (block 212). When the status of the PDs 156(1)-156(Q)connected to the powered communications ports 158(1)-158(Q) is received(block 214), the status is sent by the controller 176 to the HEC 44(block 216). The controller 176 then powers on the RXU modules160(1)-160(Z) if present and not already switched on (blocks 204, 206,208).

FIG. 11 is a flowchart illustrating an exemplary power managementprocess provided by an RAU 14 to manage power provided to PDs156(1)-156(Q) when the status of the powered communications ports158(1)-158(Q) provided in an RAU 14 changed (i.e., connected ordisconnected). If the status of any powered communications port158(1)-158(Q) has increased power requirements, such as by a newconnection or a connection with a PD 156 requiring more power, otherpowered communications ports 158(1)-158(Q) may be required to bedisabled to remain within the available power budget. If the status ofany powered communications ports 158(1)-158(Q) has decreased powerrequirements, other powered communications ports 158(1)-158(Q) may beable to be enabled and still remain within the available power budget.

With reference to FIG. 11, the controller 176 determines if theconfiguration of the RAU 14 has changed (block 220). If changed (block222), the controller 176 determines if the change is due to a change instatus of a powered communications ports 158(1)-158(Q) in the RAU 14(block 224). In this example, power is managed for two (2) poweredcommunications ports 158(1), 158(2), but any number could be managed. Ifa powered communications port 158(1)-158(Q) has not changed, this meansthat the available power budget to provide power to the PDs156(1)-156(Q) has changed since at least one module 152, 154,160(1)-160(Z) has either been removed or added to the RAU 14. In thisinstance, the controller 176 determines if a PD 156(1) is connected tothe first powered communications port 158(1) that is unpowered (block226). If so, the controller 176 determines if the available power budgetis sufficient to provide power to the PD 156(1) connected to the firstpowered communications port 158(1) (block 228). If so, the controller176 directs the PSE 170 to provide power to the first poweredcommunications port 158(1) (block 230). If not, the controller 176checks the status of the second powered communications port 158(2)(block 232).

If the controller 176 determines that the first powered communicationsport 158(1) is not powered (block 226), the controller 176 determines ifa PD 156(2) is connected to a second powered communications port 158(2)that is unpowered (block 232). If so, the controller 176 determines ifthe available power budget is sufficient to provide power to the PD156(2) connected to the second powered communications port 158(2) (block234). If so, the controller 176 directs the PSE 170 to provide power tothe second powered communications port 158(2) (block 236). If not, thecontroller 176 does not change the power configuration of the secondpowered communications port 158(2). Thus, the controller 176 managespower to by enabling a first powered communications port 158(1) ifavailable power budget is present, and then enabling a second poweredcommunications port 158(2) if available power budget is available afterproviding power to the first powered communications port 158(1). Whenthe available power budget changes for the RAU 14, the enabling ordisabling of the powered communications ports 158(1), 158(2) isre-evaluated based on the available power budget.

If the status of the powered communications ports 158(1), 158(2) haschanged (block 224), the current power settings of the poweredcommunications ports 158(1), 158(2) is also re-evaluated. In thisregard, if the first powered communications port 158(1) is connected(block 238), the controller 176 obtains the class of the PD 156(1)connected to the powered communications port 158(1) from the PSE 170(block 240). The controller 176 determines if the available power budgetis sufficient to power the PD 156(1) at its class rating (block 242). Ifso, the controller 176 directs the PSE 170 to enable the poweredcommunications port 158(1) to provide power to the PD 156(1) connectedto the powered communications port 158(1) (block 244). For example, ifthe available power budget is 16 Watts, a PoE Class 3 PD 156(1) rated at15.4 Watts connected to a powered communications port 158(1) can bepowered, and thus the powered communications port 158(1) is enabled.However, if a PoE Class 4 PD 156(1) rated at 30 Watts or less isconnected to a powered communications port 158(1), the poweredcommunications port 158(1) is disabled since the available power budgetis less than 30 Watts.

The available power budget for the RAU 14 is updated by the controller176 in memory 178 based on the class of the PD 156(1) connected to thepowered communications port 158(1) (block 246) so that power is notdirected to the second powered communications port 158(2) if there isnot sufficient power budget remaining. If the available power budget isnot sufficient to power the PD 156(1) connected to the poweredcommunications port 158(1) (block 242), the controller 176 disables thepowered communications port 158(1) so that power is not made availableby the PSE 170 to the powered communications port 158(1) (block 248).

If a PD 156(1) is not connected to the first powered communications port158(1) (block 238), the controller 176 determines if the first poweredcommunications port 158(1) is disconnected (block 249). If not, thecontroller 176 determines if a PD 156(2) is connected to the secondpowered communications port 158(2) (block 250). If so, the controller176 obtains the class of the PD 156(2) connected to the poweredcommunications port 158(2) from the PSE 170 (block 252). The controller176 determines if the available power budget is sufficient to power thePD 156(2) at its class rating (block 254). If so, the controller 176directs the PSE 170 to enable the powered communications port 158(2) toprovide power to the PD 156(2) connected to the powered communicationsport 158(2) (block 256). The available power budget for the RAU 14 isupdated by the controller 176 in memory 178 based on the class of the PD156(2) connected to the powered communications port 158(2) (block 246)to so that power is not directed to the other powered communicationsport 158(1) if there is not sufficient power budget remaining. If theavailable power budget is not sufficient to power the PD 156(2)connected to the powered communications port 158(2) (block 254), thecontroller 176 disables the powered communications port 158(2) so thatpower is not made available by the PSE 170 to the powered communicationsport 158(2) (block 258).

FIG. 12 is a more detailed diagram of one embodiment of the DDS module154 in FIG. 8 that can be provided in an RAU 14 to provide digital dataservices to the PDs 156(1)-156(Q) connected to the poweredcommunications ports 158(1)-158(Q) and to provide power management forthe powered communications ports 158(1)-158(Q), as described above. Asillustrated in FIG. 12, the DDS module 174 includes a transmit opticalsub-assembly (TOSA) 260 and a receive optical sub-assembly (ROSA) 262 toconvert downlink optical digital signals 130D from the downlink opticalfiber 135D to downlink electrical digital signals and convert uplinkelectrical digital signals to uplink optical digital signals 130U. A DDSswitch 264 is provided to switch digital data services to the poweredcommunications ports 158(1)-158(Q). The controller 176 is provided as aPoE PSE controller to manage power provided to the poweredcommunications ports 158(1)-158(Q). A power interface 266 is provided toreceive power from the power line 171 from the RF communications module152. Switches 268 and light emitting diodes (LEDs) 270 are provided toallow configuration settings and to provide the status of the DDS module174, respectively.

FIG. 13 is a schematic diagram representation of an exemplary electronicdevice 280 in the exemplary form of an exemplary computer system 282adapted to execute instructions from an exemplary computer-readablemedium to perform the power management functions. The electronic device280 may be the DDS module 154, but could be any other module or deviceprovided in the RAU 14. The electronic device 280 could be providedseparately from the other modules 152, 154, 160(1)-160(Z) that can beconfigured for the RAU 14. In this regard, the electronic device 280 maycomprise the computer system 282 within which a set of instructions forcausing the electronic device 280 to perform any one or more of themethodologies discussed herein may be executed. The electronic device280 may be connected (e.g., networked) to other machines in a LAN, anintranet, an extranet, or the Internet. The electronic device 280 mayoperate in a client-server network environment, or as a peer machine ina peer-to-peer (or distributed) network environment. While only a singledevice is illustrated, the term “device” shall also be taken to includeany collection of devices that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein. The electronic device 280 may be aserver, a personal computer, a desktop computer, a laptop computer, apersonal digital assistant (PDA), a computing pad, a mobile device, orany other device, and may represent, for example, a server or a user'scomputer.

The exemplary computer system 282 includes a processing device orprocessor 284, a main memory 286 (e.g., read-only memory (ROM), flashmemory, dynamic random access memory (DRAM) such as synchronous DRAM(SDRAM), etc.), and a static memory 288 (e.g., flash memory, staticrandom access memory (SRAM), etc.), which may communicate with eachother via a bus 290. Alternatively, the processing device 284 may beconnected to the main memory 286 and/or the static memory 288 directlyor via some other connectivity means. The processing device 284 may bethe controller 176, and the main memory 286 or static memory 288 may bethe memory 178.

The processing device 284 represents one or more general-purposeprocessing devices such as a microprocessor, central processing unit, orthe like. More particularly, the processing device 284 may be a complexinstruction set computing (CISC) microprocessor, a reduced instructionset computing (RISC) microprocessor, a very long instruction word (VLIW)microprocessor, a processor implementing other instruction sets, orprocessors implementing a combination of instruction sets. Theprocessing device 284 is configured to execute processing logic ininstructions 292 for performing the operations and steps discussedherein.

The computer system 282 may further include a network interface device294. The computer system 282 also may or may not include an input 296 toreceive input and selections to be communicated to the processing device284 when executing instructions. The computer system 282 also may or maynot include an output 298, including but not limited to a display, avideo display unit (e.g., a liquid crystal display (LCD) or a cathoderay tube (CRT)), an alphanumeric input device (e.g., a keyboard), and/ora cursor control device (e.g., a mouse).

The computer system 282 may or may not include a data storage devicethat includes instructions 300 stored in a computer-readable medium 302embodying any one or more of the RAU 14 power management methodologiesor functions described herein. The instructions 300 may also reside,completely or at least partially, within the main memory 286 and/orwithin the processing device 284 during execution thereof by thecomputer system 282, the main memory 286 and the processing device 284also constituting computer-readable media. The instructions 300 mayfurther be transmitted or received over a network 304 via the networkinterface device 294.

While the computer-readable medium 302 is shown in an exemplaryembodiment to be a single medium, the term “computer-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“computer-readable medium” shall also be taken to include any mediumthat is capable of storing, encoding or carrying a set of instructionsfor execution by the processor and that cause the processor to performany one or more of the methodologies of the embodiments disclosedherein. The term “computer-readable medium” shall accordingly be takento include, but not be limited to, solid-state memories, optical andmagnetic media, and carrier wave signals.

The DDS modules disclosed herein may be provided any type of digitaldata services. The powered communications ports provided in the RAU maybe provided to meet any power standard. In the example of PoE, IEEE802.3at specifies that link layer discovery protocol (LLDP) may be usedand supported by the components described herein, including thecontrollers and power management components in the RAUs. LLDP allowsexchange of data with PDs to determine the power rating of the PD. Also,more precise information regarding power requirements can only beexchanged using LLDP for media endpoint devices, such as LLDP-MED,according to TIA-1057). LLDP-MED allows requesting of power by PDsbetween 0 and 102.3 Watts in 0.1 Watt steps. LLDP and LLDP-MED are layer2 protocols, which require a means to receive and transmit thoseEthernet packets from and to PDs. This can be performed by thecontrollers disclosed herein and provided in the RAUs having an Ethernetmedia access controller connected to an Ethernet switch inside the mediaconverter. Alternatively, power ratings for a PD could be providedmanually or programmed into the RAUs by an operator accessing the RAUsin the distributed antenna system.

The embodiments disclosed herein include various steps. The steps of theembodiments disclosed herein may be performed by hardware components ormay be embodied in machine-executable instructions, which may be used tocause a general-purpose or special-purpose processor programmed with theinstructions to perform the steps. Alternatively, the steps may beperformed by a combination of hardware and software.

The embodiments disclosed herein may be provided as a computer programproduct, or software, that may include a machine-readable medium (orcomputer-readable medium) having stored thereon instructions, which maybe used to program a computer system (or other electronic devices) toperform a process according to the embodiments disclosed herein. Amachine-readable medium includes any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputer). For example, a machine-readable medium includes amachine-readable storage medium (e.g., read only memory (“ROM”), randomaccess memory (“RAM”), magnetic disk storage media, optical storagemedia, flash memory devices, etc.), a machine-readable transmissionmedium (electrical, optical, acoustical or other form of propagatedsignals (e.g., carrier waves, infrared signals, digital signals, etc.),etc.

Unless specifically stated otherwise as apparent from the previousdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “processing,” “computing,”“determining,” “displaying,” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission, or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear from the description above.In addition, the embodiments described herein are not described withreference to any particular programming language. It will be appreciatedthat a variety of programming languages may be used to implement theteachings of the embodiments as described herein.

Those of skill in the art would further appreciate that the variousillustrative logical blocks, modules, circuits, and algorithms describedin connection with the embodiments disclosed herein may be implementedas electronic hardware, instructions stored in memory or in anothercomputer-readable medium and executed by a processor or other processingdevice, or combinations of both. The components of the distributedantenna systems described herein may be employed in any circuit,hardware component, integrated circuit (IC), or IC chip, as examples.Memory disclosed herein may be any type and size of memory and may beconfigured to store any type of information desired. To clearlyillustrate this interchangeability, various illustrative components,blocks, modules, circuits, and steps have been described above generallyin terms of their functionality. How such functionality is implementeddepends upon the particular application, design choices, and/or designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a processor, a Digital Signal Processor (DSP), anApplication Specific Integrated Circuit (ASIC), a Field ProgrammableGate Array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. A controllermay be a processor. A processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The embodiments disclosed herein may be embodied in hardware and ininstructions that are stored in hardware, and may reside, for example,in Random Access Memory (RAM), flash memory, Read Only Memory (ROM),Electrically Programmable ROM (EPROM), Electrically ErasableProgrammable ROM (EEPROM), registers, a hard disk, a removable disk, aCD-ROM, or any other form of computer-readable medium known in the art.An exemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a remote station. In the alternative, theprocessor and the storage medium may reside as discrete components in aremote station, base station, or server.

It is also noted that the operational steps described in any of theexemplary embodiments herein are described to provide examples anddiscussion. The operations described may be performed in numerousdifferent sequences other than the illustrated sequences. Furthermore,operations described in a single operational step may actually beperformed in a number of different steps. Additionally, one or moreoperational steps discussed in the exemplary embodiments may becombined. It is to be understood that the operational steps illustratedin the flow chart diagrams may be subject to numerous differentmodifications as will be readily apparent to one of skill in the art.Those of skill in the art would also understand that information andsignals may be represented using any of a variety of differenttechnologies and techniques. For example, data, instructions, commands,information, signals, bits, symbols, and chips that may be referencedthroughout the above description may be represented by voltages,currents, electromagnetic waves, magnetic fields or particles, opticalfields or particles, or any combination thereof.

Further, as used herein, it is intended that the terms “fiber opticcables” and/or “optical fibers” include all types of single mode andmulti-mode light waveguides, including one or more optical fibers thatmay be upcoated, colored, buffered, ribbonized and/or have otherorganizing or protective structures in a cable such as one or moretubes, strength members, jackets or the like. The optical fibersdisclosed herein can be single mode or multi-mode optical fibers.Likewise, other types of suitable optical fibers includebend-insensitive optical fibers, or any other expedient of a medium fortransmitting light signals. An example of a bend-insensitive, or bendresistant, optical fiber is ClearCurve® Multimode fiber commerciallyavailable from Corning Incorporated. Suitable fibers of this type aredisclosed, for example, in U.S. Patent Application Publication Nos.2008/0166094 and 2009/0169163, the disclosures of which are incorporatedherein by reference in their entireties.

Many modifications and other embodiments of the embodiments set forthherein will come to mind to one skilled in the art to which theembodiments pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings.

What is claimed is:
 1. A non-transitory computer-readable medium storingone or more programs, the one or more programs comprising instructions,which when executed by a remote unit controller in at least one remoteunit configured to provide wireless communications and provided in adistributed communications system, cause the remote unit controller to:receive an available power budget from a remote unit controller for atleast one powered port in a remote unit provided in the distributedcommunications system, the remote unit configured to provide power to atleast one external power-consuming device connected to the at least onepowered port based on power required by at least one power-consumingremote unit module; determine a device class of the at least oneexternal power-consuming device connected to the at least one poweredport; enable power for the at least one powered port if the availablepower budget is sufficient to power the at least one externalpower-consuming device connected to the at least one powered port; anddisable the at least one powered port if the available power budget isnot sufficient to power the at least one external power-consuming deviceconnected to the at least one powered port.
 2. The non-transitorycomputer-readable medium of claim 1, wherein the instructions arefurther configured to cause the remote unit controller to disable powerfor the at least one powered port if the available power budget is notsufficient to power the at least one external power-consuming device ofthe device class.
 3. The non-transitory computer-readable medium ofclaim 2, wherein the instructions are further configured to cause theremote unit controller to determine if a status of the at least onepowered port has changed.
 4. The non-transitory computer-readable mediumof claim 3, wherein the instructions are further configured to cause theremote unit controller to enable power for the at least one powered portif the available power budget is sufficient to power the at least oneexternal power-consuming device of the device class.
 5. Thenon-transitory computer-readable medium of claim 4, wherein the deviceclass is selected from the group consisting of: an RF communicationsmodule configured to provide RF communications services and a digitaldata services (DDS) module configured to provide DDS.
 6. Anon-transitory computer-readable medium storing one or more programs,the one or more programs comprising instructions, which when executed bya remote unit controller in at least one remote unit configured toprovide wireless communications and provided in a distributed antennasystem, cause the remote unit controller to: receive an available powerbudget from a remote unit controller for at least one powered port in aremote unit provided in the distributed antenna system, the remote unitconfigured to provide power to at least one external power-consumingdevice connected to the at least one powered port based on powerrequired by at least one power-consuming remote unit module; enablepower for the at least one powered port if the available power budget issufficient to power the at least one external power-consuming deviceconnected to the at least one powered port; and disable the at least onepowered port if the available power budget is not sufficient to powerthe at least one external power-consuming device connected to the atleast one powered port.
 7. The non-transitory computer-readable mediumof claim 6, wherein the instructions are further configured to cause theremote unit controller to disable the at least one powered portcomprised of at least one first port among a plurality of powered portsif the available power budget is only sufficient to power the at leastone external power-consuming device connected to at least one secondport among the plurality of powered ports.
 8. The non-transitorycomputer-readable medium of claim 7, further comprising determining if astatus of the at least one powered port has changed.
 9. Thenon-transitory computer-readable medium of claim 8, wherein theinstructions are further configured to cause the remote unit controllerto determine a device class of the at least one external power-consumingdevice connected to the at least one powered port.
 10. Thenon-transitory computer-readable medium of claim 9, wherein theinstructions are further configured to cause the remote unit controllerto enable power for the at least one powered port if the available powerbudget is sufficient to power the at least one external power-consumingdevice of the device class.
 11. The non-transitory computer-readablemedium of claim 9, wherein the instructions are further configured tocause the remote unit controller to disable power for the at least onepowered port if the available power budget is not sufficient to powerthe at least one external power-consuming device of the device class.12. The non-transitory computer-readable medium of claim 11, wherein thedevice class is selected from the group consisting of: an RFcommunications module configured to provide RF communications servicesand a digital data services (DDS) module configured to provide DDS. 13.A non-transitory computer-readable medium storing one or more programs,the one or more programs comprising instructions, which when executed bya remote unit controller in at least one remote unit configured toprovide wireless communications and provided in a distributedcommunication system, cause the remote unit controller to: receive anavailable power budget from a remote unit controller for at least onepowered port in a remote unit provided in the distributed communicationsystem, the remote unit configured to provide power to at least oneexternal power-consuming device connected to the at least one poweredport based on power required by at least one power-consuming remote unitmodule; enable power for the at least one powered port if the availablepower budget is sufficient to power the at least one externalpower-consuming device connected to the at least one powered port; anddisable the at least one powered port comprised of at least one firstport among a plurality of powered ports if the available power budget isonly sufficient to power the at least one external power-consumingdevice connected to at least one second port among the plurality ofpowered ports.
 14. The non-transitory computer-readable medium of claim13, further comprising determining if a status of the at least onepowered port has changed.
 15. The non-transitory computer-readablemedium of claim 13, wherein the instructions are further configured tocause the remote unit controller to determine a device class of the atleast one external power-consuming device connected to the at least onepowered port.
 16. The non-transitory computer-readable medium of claim15, wherein the instructions are further configured to cause the remoteunit controller to enable power for the at least one powered port if theavailable power budget is sufficient to power the at least one externalpower-consuming device of the device class.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the instructions arefurther configured to cause the remote unit controller to disable powerfor the at least one powered port if the available power budget is notsufficient to power the at least one external power-consuming device ofthe device class.
 18. The non-transitory computer-readable medium ofclaim 17, wherein the device class is selected from the group consistingof: an RF communications module configured to provide RF communicationsservices and a digital data services (DDS) module configured to provideDDS.
 19. The non-transitory computer-readable medium of claim 15,wherein the instructions are further configured to cause the remote unitcontroller to determine a device class of the at least one externalpower-consuming device connected to the at least one second port amongthe plurality of powered ports.